https://perconadev.atlassian.net/browse/K8SPXC-1461

DESCRIPTION

Problem:
In situations where storage resources are limited and we attempt to resize PVCs, some PVCs may be successfully resized while others fail. In this case, we log only the PVCs that failed to resize, without logging the PVCs that were resized successfully.

Solution:
Create a warning Event on exceeded quota and storageclass that provisions the pvc must support resize errors for each failed PVC update. The operator will depend on these events to get information about each PVC resize failure. The operator should wait until all PVC resize operations are either completed or failed, ensuring that all PVC resize results are logged. Only then, it should revert the PVC size in the cr.yaml.

CHECKLIST

Jira

• Is the Jira ticket created and referenced properly?
• Does the Jira ticket have the proper statuses for documentation (Needs Doc) and QA (Needs QA)?
• Does the Jira ticket link to the proper milestone (Fix Version field)?

Tests

• Is an E2E test/test case added for the new feature/change?
• Are unit tests added where appropriate?
• Are OpenShift compare files changed for E2E tests (compare/*-oc.yml)?

Config/Logging/Testability

• Are all needed new/changed options added to default YAML files?
• Are all needed new/changed options added to the Helm Chart?
• Did we add proper logging messages for operator actions?
• Did we ensure compatibility with the previous version or cluster upgrade process?
• Does the change support oldest and newest supported PXC version?
• Does the change support oldest and newest supported Kubernetes version?